June 17, 2007
Cellocator is announcing the release of an extended Geo-Fence functionality from firmware 25h and on:
- The Geo—Fence can be defined as “Keep In”, “Keep Out”, “Hot-Spot” (trigger on both entering and leaving), “Modem Off zone” and “Way Point”
- The triggered message will include the index of violated Geo-Fence
Note: New Cellocator Programmer (5.1.0.19 or above) is required to support new geo-fence types.
New geofences logic has the following :
Extended geofence slot bitmap -- 2 bytes, starting from address 467 (decimal).
Slot types:
|
Extended
type flag |
Fence type
bit 1 |
Fence type
bit 0 |
Meaning |
|
0 |
0 |
0 |
Geofence slot empty - ignored |
|
0 |
0 |
1 |
Waypoint |
|
0 |
1 |
0 |
Keep-out |
|
0 |
1 |
1 |
Keep-in |
|
1 |
0 |
0 |
Geo hot spot |
|
1 |
0 |
1 |
No modem zone |
Other values are reserved.
Fence logic (bit 5, byte 6 in EEPROM):
0: Global context mode
1: Discrete context mode
New behaviour:
- Waypoints behaviour is similar to prior versions, but now more than one waypoint may be active at a given time.
- Global context mode (fence logic = 0):
- Keep in fences logic:
- When position changes, trigger is generated if both the following terms are true:
- In the new position *ALL* keep-in fences are in violation state (meaning - position is outside all keep-in fences).
- Previously at least one of the fences wasn't in violation state (position was in the area of at least one of the fences).
- Trigger's transmission-reason-specific data is the index of latest slot that changed its status to violation state.
- Keep out fences logic:
- When position changes, trigger is generated if both the following terms are true:
- In the new position at least one of the fences is in violation state (meaning - position is inside one of the keep-out fences).
- Previously *ALL* keep-out fences weren't in violation state (position was outside the area of all keep-out fences).
- Trigger's transmission-reason-specific data is the index of latest slot that changed its status to violation state.
- Discrete context mode (fence logic = 1):
- Triggers are generated discretely for violation of each keep-in/out fence, regardless of other fences status.
- Trigger's transmission-reason-specific data is the index of the slot that changed its status to violation state.
- Geo hot spot:
- Generates trigger on entry and exit.
- Transmission reason T_R_GEO_HOT_SPOT_TRAVERSAL = 191.
- Trigger's transmission-reason-specific data: Bits 0-6 is the index of the slot. Most significant bit (bit 7) indicates direction: entry to hot spot ("1") or exit from hot spot ("0").
- Behaviour is not affected by fence logic bit.
- No modem zone
- Generates trigger when shutting down modem as a result of entry to "no modem zone".
- Trigger is generated only for the first fence, that causes the modem's shutdown. On entry to other "no modem" zones, while modem is already turned off, no more triggers are generated.
- Transmission reason T_R_NO_MODEM_ZONE_ENTRY = 190.
- Modem is shut down when unit is inside "no modem zone", regardless of trigger settings.
The firmware for Compact Fleet unit is attached (equipped by Telit 3 modem).
telemetry file for Commap
|
For evaluating the new firmware version
please contact technical support at Cellocator | | 
